Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1289

reference: 176-tree-1
name: 1289
tree-preservation-order: undefined
176-tpo-1
uprn
address-text
point: POINT (-0.938021 50.867255)
geometry: MULTIPOLYGON (((-0.937851 50.867237,-0.937859 50.867270,-0.937882 50.867300,-0.937919 50.867325,-0.937967 50.867340,-0.938019 50.867346,-0.938072 50.867341,-0.938120 50.867327,-0.938158 50.867303,-0.938183 50.867273,-0.938192 50.867240,-0.938185 50.867206,-0.938161 50.867176,-0.938124 50.867152,-0.938077 50.867136,-0.938024 50.867130,-0.937971 50.867135,-0.937923 50.867150,-0.937885 50.867174,-0.937860 50.867203,-0.937851 50.867237)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL